Error Codes & Actions List
Error Codes and Actions
The following table lists the error codes, alert messages, and recommended actions.
| Error Codes | Alert Message | Recommended Action |
|---|---|---|
| E10000 | Generic Errors | |
| E10001 | License has expired. Shutting Down | Contact your sales representative or support for a valid license key. |
| E10002 | Failed to start RSControl | Check rscontrol.log and see why RSControl is unable to start up correctly. |
| E10003 | Failed to start RSView | Check rsview.log and Catalina. Out and see why RSView is unable to start up correctly. |
| E10004 | Failed to start RSMgmt | Check the rsmgmt.log and see why the RSMgmt is unable to start up correctly. |
| E10005 | Failed to start RSRemote | Check the rsremote.log and see why the RSRemote is unable to start up correctly. |
| E10006 | Licensed IP Address violated. Shutting Down | Please contact your sales representative or support for a valid license key. |
| E10007 | Resolve License violated for maximum number of core | Resolve Actions Pro will shut down in two weeks if the violation is left unresolved. Contact support for a license with more cores. |
| E10008 | Resolve License violated for Community Edition with Multiple Hosts. Shutting Down | Actions Pro Community Edition must run all components in one server. Contact support for a valid license. |
| E10009 | Maximum memory limit violated for Resolve license | Actions Pro will shutdown in 2 weeks if the violation is left unresolved. Contact support for a license with more memories. |
| E10010 | Component process id does not match value in the lock file | Check if the component was started correctly and that no duplicate process exists. |
| E10011 | Component is running without a lock file | Check if the component was started correctly and that no duplicate process exists. |
| E10012 | Component is down but still has a lock file | Check if the component was stopped correctly and that it did not crash. |
| E10013 | Component stdout log file cannot be found | Component is missing its stdout file, it cannot be monitored. |
| E10014 | Component stdout error detected | Component stdout error detected. |
| E10015 | Number of Users limit violated for Resolve license | Actions Pro will shut down in 2 weeks if the violation left unresolved - either delete Actions Pro users or contact support for a license with more end-users. |
| E10016 | Number of Admin Users limit violated for Resolve license | Actions Pro will shutdown in 2 weeks if the violation left unresolved - either delete Actions Pro users or contact support for a license with more end-users. |
| E10017 | Resolve license violated for Gateway | Actions Pro license violated for gateway. |
| E10018 | RSRemote is unresponsive | RSRemote is unresponsive. |
| E10019 | Resolve license deleted | Actions Pro license deleted. |
| E10020 | Resolve license violated for High Availability (HA). Shutting Down | Contact support for a valid license. |
| E10021 | Resolve Gateway license expired | Actions Pro gateway license expired. |
| E20000 | Database Errors | |
| E20001 | DB Gateway failed to load SQL driver | Check if the RSRemote has the gateway turned on and the appropriate DB driver is included in the class path. |
| E20002 | DB Gateway failed to initialize gateway | Check if the database connection details is correct and verify connectivity to the database from Actions Pro. |
| E20003 | Missing SQL database driver | Check if the DB driver is active in the run.sh. For Windows, ensure that the service was installed with the driver active. |
| E20004 | Failed to initialize Graph DB | Ensure that all RSZK(s) are running before starting RSView - check that RSZK is running and able to establish connection from zk.sh / zk.bat. Contact support. |
| E20005 | The DB Status Check Failed, either due to a failure to connect, or a slow response from the DB | Check if the connection details in RSMgmt are correct and that the DB is behaving normally. |
| E20006 | Failed to initialize custom tables | Check if the connection details in RSMgmt are correct and that the DB is behaving normally. |
| E20007 | Failed to reinitialize Hibernate | Check the database and database connection. |
| E20008 | ESB Heartbeat Timeout | Failed to receive ESB Heartbeat message before timeout - check if RSMQ service is running, if the ESB configuration is correct, and if the network connection between this server and the RSMQ is not down or blocked. |
| E30000 | Scheduler and Execution Errors | |
| E30001 | Failed to initialize Job Scheduler / CronScheduler | RSControl needs to be restarted and verified that it started correctly. |
| E40000 | Messaging Errors | |
| E40001 | Failed to find / initialize receive Queue | Check component is able to connect to RSMQ. Check RSMQ Configuration is using correct IP address. |
| E50000 | Gateway and Adapter Errors | |
| E50001 | Failed to connect to PRIMARY and BACKUP Netcool Object Server | Check Actions Pro connectivity to the Netcool PRIMARY and/or BACKUP Object Server. |
| E50002 | Failed to initialize Remedy Gateway | Check Actions Pro connectivity to the Remedy server. |
| E50003 | Failed to connect to PRIMARY and BACKUP TSRM Server | Check Actions Pro connectivity to the TSRM PRIMARY and/or BACKUP Server. |
| E60000 | Security Errors | |
| E60001 | Failed to connect to Active Directory server | Check Actions Pro connectivity to the Active Directory server |
| E60002 | Failed to connect to LDAP server | Check Actions Pro connectivity to the LDAP server |
| E60003 | Missing resolve.maint authentication file | Check that the WEB-INF/users/resolve.maint file exists. |
| E70000 | System and Resource Errors | |
| E70001 | Low available memory | Check the memory usage on the component using RSConsole internal/jvminfo. The -Xmx max heap memory may be needed to be increased. |
| E70002 | THREADPOOL MAXED for 20mins - no new JMS message have been processed | Restart the component that threw this error. |
| E80000 | Metric Threshold Errors | |
| E80001 | Check metric thresholds | Check metric thresholds. |
| E90000 | Miscellaneous Errors | |
| E99999 | Test message | This is a test error code only. |